We are working with Exchange 2007. We have been using Active Directory for some time and have extended the schema with a number of organization specific LDAP attributes that we use for a number of applications. Now I need to create some Exchange custom address lists and need to know if I can use our existing attributes. I know I could populate and use extensionAttribute1 through 15, but we haven't done this and I am hoping I don't have to. I would prefer just to use the custom attributes I have already created and populated for this purpose. I this possible, or are custom address list queries limited to the built-in extensionAttribute1 through 15? Thanks! Al

Hi, CustomAttributes1 - 15 are used for various purposes to filter out the objects but as you said if you already have created and using some custom LDAP attributes, I would suggest that you try enumerating the objects by filtering attribute what you created but not sure as of yet whether you can use any Custom LDAP attribute to filter out the results to create an address list. Please refer the list of attributes you can use to filter the recipients to create an address lists. http://technet.microsoft.com/en-us/library/bb430771.aspx I hope this helps. Thanks.Vishal Ramnani | MCITP - Exchange 2007 | MCSE Messaging | MCTS - Win 2008 Config

Yes, you can use the cutom attributes to segregate your address lists provided the filter you create for each address list should be accurate.As far as Exchange queries to AD are concerned they are always simple LDAP queries with few exceptions and few complications. So yes, AD can return all results correctly if the filter is written correctly. There isnt any document supporting it I believe. Yet, you may want to check if this is supported or not.Milind Naphade | MCTS:M | http://www.msexchangegeek.com

I think you are very wrong here. The problem is that Exchange 2007 does not support LDAP for custom address lists anymore. Now it is changed to OPATH filters, and they don't appear to be as flexible. This means you'll have to stick to the attributes described here: http://technet.microsoft.com/en-us/library/bb738157.aspx And this again means that custom schema extensions cannot be used.

Yes, extensionAttribute1-15 attributes are supported to fill up for setting up custom address list, moreover there are many or almost all attributes can be used in filter as per the link given by Vishal. However I would keep extensionAttribute1-15 empty if I have any plan to add attribute in GAL which is not available by default while customizing Exchange Detail Templates, unless you don't have any other choice because there you can use anyone of these attributes only to be in Microsoft support boundary. Further info on Details Templates... Exchange Details Templates http://www.messagingtalk.org/exchange-details-templates Amit Tank | MVP Exchange Server | MCITP: EMA | MCSA: M | http://ExchangeShare.WordPress.com

Thanks It is beginning to look like I am out of luck as far as my schema attributes go. One thing is still confusing me though: If I am using the OPATH-type filter to create my address list... Is the address-list filter looking to the AD objects (through a Powershell ADSI object or a Powershell DirectoryServices.DirectorySearcher type query) or are the OPATH filters calling records/objects from some Exchange internal data store representation of the GAL? Thanks, Al

@Jon-Alfred. You are correct. I didnt not read that he is running Exchange 2007 or may be ingored it completely. @alatmcc:Yes address lists filters using OPATH will still look at AD objects. Exchange 2007 still uses AD to build Address lists. apart from OABs, Exchange does not store the ALs anywhere AFAIK. What I understood from your first post was, you have some custom schema extensionsand you want to use those attributes to filter the recipient objects. If I havent missunderstood it then you may not be able to filter them. The other way around is to use the way suggested by Amit.Milind Naphade | MCTS:M | http://www.msexchangegeek.com

Thanks, everyone. I just copied my custom schema attribute values to a few of the extensionAttributes and it is working fine. The OPATH approach just seems so odd to me.... enumerating every object and pumping it through the object pipeline, just to get a result set that the active directory service is designed to deliver efficiently through an LDAP query, just seems like such a kludge..... Thanks Again! Al